Add E2E integration test for lightspeed-agentic-alerts-adapter - #83711

🏁 Script executed:

#!/bin/bash
set -eu

file='ci-operator/config/openshift/lightspeed-agentic-alerts-adapter/openshift-lightspeed-agentic-alerts-adapter-main.yaml'

printf '%s\n' '--- changed files ---'
git status --short
printf '%s\n' '--- diff stat ---'
git diff --stat
printf '%s\n' '--- target file ---'
cat -n "$file"
printf '%s\n' '--- owner references in nearby CI configuration ---'
rg -n -C 3 'owner:|cluster_claim|lightspeed-agentic-alerts-adapter' ci-operator/config/openshift/lightspeed-agentic-alerts-adapter ci-operator/config/openshift 2>/dev/null | head -300
printf '%s\n' '--- repository instructions and generation targets ---'
rg -n -C 3 'make (update|registry-metadata|ci-operator-config|jobs)|zz_generated_metadata|Prow|owner.*cluster' Makefile* README* ci-operator 2>/dev/null | head -300

Repository: openshift/release

Length of output: 50373

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- cluster-pool owner definitions ---'
rg -n -C 5 '(^|[[:space:]])(osa|obs)(:|$)|owner' core-services/cluster-pools 2>/dev/null | head -250

printf '%s\n' '--- cluster-claim owner documentation and implementation references ---'
rg -n -C 4 'cluster_claim|cluster claim|cluster-pool|cluster pool|owner.*cloud|cloud.*owner' \
  README.md CONTRIBUTING.md Makefile ci-operator core-services 2>/dev/null \
  | grep -E 'cluster_claim|cluster claim|cluster.pool|cluster-pool|owner.*cloud|cloud.*owner|owner:' \
  | head -300

printf '%s\n' '--- relevant Makefile targets ---'
sed -n '80,135p' Makefile
printf '%s\n' '--- generation-related files ---'
git ls-files | grep -E '(^|/)(zz_generated_metadata|prow|jobs|config)' | grep -E 'lightspeed-agentic-alerts-adapter|ci-operator' | head -200

printf '%s\n' '--- all configurations for this repository ---'
git ls-files 'ci-operator/config/openshift/lightspeed-agentic-alerts-adapter/*' \
  | while read -r f; do echo "### $f"; rg -n 'cluster_claim|owner:|promotion:|zz_generated_metadata|workflow:|always_run:|optional:' "$f" || true; done

Repository: openshift/release

Length of output: 50375

🌐 Web query:

OpenShift ci-operator cluster_claim owner field cluster pool owner documentation

💡 Result:

In OpenShift CI, the owner field within the cluster_claim stanza is a mandatory label used to identify and select a specific cluster pool from which to claim an ephemeral cluster [1][2][3]. When a CI job is configured to use a cluster_claim, the ci-operator uses the provided metadata—architecture, cloud, owner, product, and version—to match against the labels defined on available cluster pools [1][2]. The owner label acts as a filter to ensure the job claims a cluster from the correct pool [1]. Key points regarding the owner field: - Purpose: It identifies the team or entity responsible for the cluster pool (e.g., openshift-ci, dptp-demo, or hypershift) [1][4]. - Matching: The value specified in the ci-operator configuration must match a corresponding owner label on the target cluster pool [1][2]. - Usage Policy: Cluster pools owned by openshift-ci are maintained by the DPTP team and are generally available for tests within the openshift organization [1]. Pools with different owners are intended for specific use cases and should only be accessed with the knowledge and approval of their respective owners [1]. - Configuration Example: tests: - as: example-test cluster_claim: architecture: amd64 cloud: aws owner: openshift-ci product: ocp timeout: 1h0m0s version: "4.18" For teams setting up their own cluster pools, the owner label is defined in the pool manifest applied to the hosted-management cluster [1]. Currently, authorization to use specific pools is not strictly enforced programmatically, but reliance on the owner field is the standard mechanism for managing cluster pool access and organization [1].

Citations:

• 1: https://docs.ci.openshift.org/how-tos/cluster-claim/
• 2: https://docs.ci.openshift.org/docs/architecture/ci-operator/
• 3: https://konflux-ci.dev/docs/testing/integration/third-parties/openshift-ci/
• 4: https://github.com/openshift/release/blob/main/ci-operator/step-registry/jira-agent/ONBOARDING.md

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- exact private-pool configuration ---'
cat -n core-services/cluster-pools/_config.yaml
printf '%s\n' '--- exact ci-operator configuration and job generation targets ---'
sed -n '105,130p' Makefile
sed -n '130,175p' Makefile
printf '%s\n' '--- generated jobs for this repository ---'
git ls-files 'ci-operator/jobs/**' | grep 'lightspeed-agentic-alerts-adapter' | head -80 || true
printf '%s\n' '--- generated metadata and Prow references ---'
git ls-files | grep 'lightspeed-agentic-alerts-adapter' | head -120
printf '%s\n' '--- ownership values for adjacent lightspeed and observability jobs ---'
rg -n -C 2 'owner: (osa|obs)|namespace: osa|repo: lightspeed-agentic-alerts-adapter' \
  ci-operator/config ci-operator/jobs 2>/dev/null | grep -E 'lightspeed|owner: (osa|obs)|namespace: osa' | head -160

Repository: openshift/release

Length of output: 30912

🌐 Web query:

site:github.com/openshift/release "owner: osa" "cluster_claim"

💡 Result:

In the context of the OpenShift CI/CD infrastructure (specifically the openshift/release repository), cluster_claim is a configuration parameter used within CI operator job definitions to request or 'claim' a pre-provisioned cluster from a cluster pool [1][2]. Instead of performing the time-consuming process of installing a new cluster for every test run, CI jobs can use cluster_claim to utilize an existing cluster that matches specific criteria, such as [2]: - architecture (e.g., amd64) - cloud provider (e.g., aws) - product (e.g., ocp) - version (e.g., 4.18) - owner (e.g., hypershift) - timeout (e.g., 2h0m0s) This mechanism is managed by components like the clusterclaims-controller [3] and relies on ClusterPool resources [4], which maintain a pool of ready-to-use clusters. When a job defines a cluster_claim, the CI infrastructure orchestrates the lease of a cluster from the specified pool for the duration of the test execution, significantly reducing CI turnaround times [1].

Citations:

• 1: https://github.com/openshift/release/blob/main/ci-operator/step-registry/generic-claim/generic-claim-workflow.yaml
• 2: https://github.com/openshift/release/blob/main/ci-operator/step-registry/jira-agent/ONBOARDING.md
• 3: https://github.com/openshift/release/blob/main/core-services/openshift-priv/_whitelist.yaml
• 4: https://github.com/openshift/release/blob/main/clusters/hosted-mgmt/hive/pools/openshift-ci/ci-ocp-5-0-amd64-aws-us-east-1_clusterpool.yaml

🌐 Web query:

site:github.com/openshift/release "owner: obs" "lightspeed"

💡 Result:

OBS Lightspeed refers to components within the Red Hat OpenShift ecosystem related to Red Hat OpenShift Lightspeed, an AI-powered assistant designed for OpenShift [1][2][3]. In the context of the openshift/release repository, which manages CI/CD configurations for OpenShift, OBS Lightspeed components appear as various software projects and services, including: 1. lightspeed-service: A service component maintained as part of the OpenShift ecosystem, with dedicated CI/CD configurations and periodic test variants [4][2]. 2. lightspeed-operator: An operator responsible for managing aspects of the Lightspeed functionality within an OpenShift cluster [1]. 3. lightspeed-agentic-operator and lightspeed-agentic-sandbox: Additional components involving agentic AI capabilities within the OpenShift framework [3]. These components are owned and maintained by the Red Hat OpenShift engineering teams, as indicated by the repository structures and OWNERS files within the openshift/release CI tooling [2][5][3]. The term OBS in this context is often associated with observability or general OpenShift build services, depending on the specific subdirectory or component being referenced [1][6][7].

Citations:

• 1: Add rhobs observability-operator 4.22 staging job on GCP #80023
• 2: https://github.com/openshift/release/pull/59043/files
• 3: 04cbd83
• 4: 7437cd1
• 5: https://github.com/openshift/release
• 6: 4aec497
• 7: e0c7578

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- all cluster_claim owner values ---'
rg -n '^[[:space:]]+owner:' ci-operator/config \
  | sed -E 's/.*owner:[[:space:]]*//' | sort | uniq -c | sort -nr | head -80

printf '%s\n' '--- exact owner values and namespaces for lightspeed-related configs ---'
rg -n -C 5 'owner:|namespace: osa|repo: lightspeed' ci-operator/config \
  | grep -B5 -A5 -E 'lightspeed|owner: (osa|obs)|namespace: osa' | head -220

printf '%s\n' '--- generated Prow job references for the target config ---'
for f in $(git ls-files 'ci-operator/jobs/openshift/lightspeed-agentic-alerts-adapter/*.yaml'); do
  echo "### $f"
  rg -n -C 2 'cluster_claim|owner:|e2e-integration|lightspeed-agentic-alerts-adapter' "$f" || true
done

Repository: openshift/release

Length of output: 31896